Oh boy. Misunderstood the function of from __future__ import annotations. Okay, this PR won't work in 3.9. Closing for now, but good to have as a reference, since we're considering dropping 3.9 support soon.

Reopening, as much of this can still hold. Just not | operations for Optional and Union, which is fine. I'll revert this (stash for later).

Update

Actually, | works for type hints. Just not for type definition, so no NewType = int | str allowed. Easy!

Codecov Report

❌ Patch coverage is 99.02200% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.26%. Comparing base (ebc9d4a) to head (bbd8a13).
⚠️ Report is 7 commits behind head on main.

@@            Coverage Diff             @@
##             main    #7026      +/-   ##
==========================================
- Coverage   79.27%   79.26%   -0.00%     
==========================================
  Files         566      566              
  Lines       43779    43805      +26     
==========================================
+ Hits        34700    34717      +17     
- Misses       9079     9088       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@edan-bainglass great to see work on typing. :-)

It seems that this partly overlaps with my work in #7019 and #6704. Would be great if you could have a look and review. Especially #6704 should go in first because some of the files that you're modifying here are not actually type-checked in pre-commit.

@edan-bainglass great to see work on typing. :-)

It seems that this partly overlaps with my work in #7019 and #6704. Would be great if you could have a look and review. Especially #6704 should go in first because some of the files that you're modifying here are not actually type-checked in pre-commit.

Okay cool. I'll have a look this week.

@danielhollas honest opinion, is this PR required? I believe you stated this type of work can be automated by ruff, once some prelim work is done, which you're addressing in recent PRs. Is this accurate?

@danielhollas honest opinion, is this PR required?

Hah, thanks, I was going to write the same thing here but was procrastinating on it as I didn't want to be a PITA. 😅

I don't think we should merge this at this point: we should wait until we drop Python 3.9, and then convert everything over whole codebase at once with ruff. Then we'll add the resulting commit to .git-blame-ignore-revs to preserve git history.

Hah, thanks, I was going to write the same thing here but was procrastinating on it as I didn't want to be a PITA. 😅

Not at all. I rather close it and have the robots handle it cleanly.

I don't think we should merge this at this point: we should wait until we drop Python 3.9, and then convert everything over whole codebase at once with ruff. Then we'll add the resulting commit to .git-blame-ignore-revs to preserve git history.

Sounds like a plan 👍 We probably should look more seriously into doing 3.9 in AiiDAlab

We probably should look more seriously into doing 3.9 in AiiDAlab

Yep, see aiidalab/aiidalab-docker-stack#455 (comment)

Most of what is done here is already accomplished by a series of recent PRs by @danielhollas. As suggested above, once we drop support for Python 3.9, we will push one commit to update all type hints across the codebase. As such, this PR is no longer necessary. Closing...